Applied artificial intelligence technology for narrative generation using an invocable analysis service and data re-organization

ABSTRACT

Disclosed herein are example embodiments of an improved narrative generation system where an analysis service that executes data analysis logic, including data re-organization logic, that supports story generation is segregated from an authoring service that executes authoring logic for story generation through an interface. Accordingly, when the authoring service needs analysis from the analysis service, it can invoke the analysis service through the interface. By exposing the analysis service to the authoring service through the shared interface, the details of the logic underlying the analysis service are shielded from the authoring service (and vice versa where the details of the authoring service are shielded from the analysis service). Through parameterization of operating variables, the analysis service can thus be designed as a generalized data analysis service that can operate in a number of different content verticals with respect to a variety of different story types.

CROSS-REFERENCE AND PRIORITY CLAIM TO RELATED PATENT APPLICATIONS

This patent application claims priority to U.S. provisional patent application Ser. No. 62/618,249, filed Jan. 17, 2018, and entitled “Applied Artificial Intelligence Technology for Narrative Generation Using an Invocable Analysis Service”, the entire disclosure of which is incorporated herein by reference.

This patent application is also related to (1) U.S. patent application Ser. No. 16/235,594, filed this same day, and entitled “Applied Artificial Intelligence Technology for Narrative Generation Using an Invocable Analysis Service”, (2) U.S. patent application Ser. No. 16/235,636, filed this same day, and entitled “Applied Artificial Intelligence Technology for Narrative Generation Using an Invocable Analysis Service with Analysis Libraries”, and (3) U.S. patent application Ser. No. 16/235,705, filed this same day, and entitled “Applied Artificial Intelligence Technology for Narrative Generation Using an Invocable Analysis Service and Configuration-Driven Analytics”, the entire disclosures of each of which are incorporated herein by reference.

INTRODUCTION

There is an ever-growing need in the art for improved natural language generation (NLG) technology that harnesses computers to process data sets and automatically generate narrative stories about those data sets. NLG is a subfield of artificial intelligence (AI) concerned with technology that produces language as output on the basis of some input information or structure, in the cases of most interest here, where that input constitutes data about some situation to be analyzed and expressed in natural language. Many NLG systems are known in the art that use template approaches to translate data into text. However, such conventional designs typically suffer from a variety of shortcomings such as constraints on how many data-driven ideas can be communicated per sentence, constraints on variability in word choice, and limited capabilities of analyzing data sets to determine the content that should be presented to a reader.

As technical solutions to these technical problems in the NLG arts, the inventors note that the assignee of the subject patent application has previously developed and commercialized pioneering technology that robustly generates narrative stories from data, of which a commercial embodiment is the QUILL™ narrative generation platform from Narrative Science Inc. of Chicago, Ill. Aspects of this technology are described in the following patents and patent applications: U.S. Pat. Nos. 8,374,848, 8,355,903, 8,630,844, 8,688,434, 8,775,161, 8,843,363, 8,886,520, 8,892,417, 9,208,147, 9,251,134, 9,396,168, 9,576,009, 9,697,198, 9,697,492, 9,720,884, 9,720,899, and 9,977,773; and U.S. patent application Ser. No. 14/211,444 (entitled “Method and System for Configuring Automatic Generation of Narratives from Data”, filed Mar. 14, 2014), Ser. No. 15/253,385 (entitled “Applied Artificial Intelligence Technology for Using Narrative Analytics to Automatically Generate Narratives from Visualization Data, filed Aug. 31, 2016), 62/382,063 (entitled “Applied Artificial Intelligence Technology for Interactively Using Narrative Analytics to Focus and Control Visualizations of Data”, filed Aug. 31, 2016), Ser. No. 15/666,151 (entitled “Applied Artificial Intelligence Technology for Interactively Using Narrative Analytics to Focus and Control Visualizations of Data”, filed Aug. 1, 2017), Ser. No. 15/666,168 (entitled “Applied Artificial Intelligence Technology for Evaluating Drivers of Data Presented in Visualizations”, filed Aug. 1, 2017), Ser. No. 15/666,192 (entitled “Applied Artificial Intelligence Technology for Selective Control over Narrative Generation from Visualizations of Data”, filed Aug. 1, 2017), 62/458,460 (entitled “Interactive and Conversational Data Exploration”, filed Feb. 13, 2017), Ser. No. 15/895,800 (entitled “Interactive and Conversational Data Exploration”, filed Feb. 13, 2018), 62/460,349 (entitled “Applied Artificial Intelligence Technology for Performing Natural Language Generation (NLG) Using Composable Communication Goals and Ontologies to Generate Narrative Stories”, filed Feb. 17, 2017), Ser. No. 15/897,331 (entitled “Applied Artificial Intelligence Technology for Performing Natural Language Generation (NLG) Using Composable Communication Goals and Ontologies to Generate Narrative Stories”, filed Feb. 15, 2018), Ser. No. 15/897,350 (entitled “Applied Artificial Intelligence Technology for Determining and Mapping Data Requirements for Narrative Stories to Support Natural Language Generation (NLG) Using Composable Communication Goals”, filed Feb. 15, 2018), Ser. No. 15/897,359 (entitled “Applied Artificial Intelligence Technology for Story Outline Formation Using Composable Communication Goals to Support Natural Language Generation (NLG)”, filed Feb. 15, 2018), Ser. No. 15/897,364 (entitled “Applied Artificial Intelligence Technology for Runtime Computation of Story Outlines to Support Natural Language Generation (NLG)”, filed Feb. 15, 2018), Ser. No. 15/897,373 (entitled “Applied Artificial Intelligence Technology for Ontology Building to Support Natural Language Generation (NLG) Using Composable Communication Goals”, filed Feb. 15, 2018), Ser. No. 15/897,381 (entitled “Applied Artificial Intelligence Technology for Interactive Story Editing to Support Natural Language Generation (NLG)”, filed Feb. 15, 2018), 62/539,832 (entitled “Applied Artificial Intelligence Technology for Narrative Generation Based on Analysis Communication Goals”, filed Aug. 1, 2017), Ser. No. 16/047,800 (entitled “Applied Artificial Intelligence Technology for Narrative Generation Based on Analysis Communication Goals”, filed Jul. 27, 2018), Ser. No. 16/047,837 (entitled “Applied Artificial Intelligence Technology for Narrative Generation Based on a Conditional Outcome Framework”, filed Jul. 27, 2018), 62/585,809 (entitled “Applied Artificial Intelligence Technology for Narrative Generation Based on Smart Attributes and Explanation Communication Goals”, filed Nov. 14, 2017), 62/632,017 (entitled “Applied Artificial Intelligence Technology for Conversational Inferencing and Interactive Natural Language Generation”, filed Feb. 19, 2018), and 62/691,197 (entitled “Applied Artificial Intelligence for Using Natural Language Processing to Train a Natural Language Generation System”, filed Jun. 28, 2018); the entire disclosures of each of which are incorporated herein by reference.

The inventors have further extended on this pioneering work with improvements in AI technology as described herein.

For example, the inventors disclose an improvement in narrative generation where an analysis service that executes data analysis logic that supports story generation is segregated from an authoring service that executes authoring logic for story generation through an interface. Accordingly, when the authoring service needs analysis from the analysis service, it can invoke the analysis service through the interface. By exposing the analysis service to the authoring service through the shared interface, the details of the logic underlying the analysis service are shielded from the authoring service (and vice versa where the details of the authoring service are shielded from the analysis service). Through parameterization of operating variables, the analysis service can thus be designed as a generalized data analysis service that can operate in a number of different content verticals with respect to a variety of different story types. This provides practitioners with more flexibility in building out new analytics as well as enabling dynamic, user-defined content.

The inventors further disclose that the analysis service can also be designed to further segregate generalized data analytics from higher level aspects of analysis via another interface. A plurality of analysis applications can be deployed by the analysis service, where the analysis applications are configured to selectively organize and invoke the execution of the lower level analytics. These analysis applications can be selected and instantiated as a function of a parameter in an analysis request from the authoring service and/or at least a portion of the structured data about which a narrative story is to be generated. The lower level analytics are then selectively parameterized and invoked by the selected analysis application. In this way, the lower level analytics can be further shielded from the particulars of a given story request and the higher level analysis applications can be tailored as a function of such particulars. This allows for further flexibility in using and re-using analytics across a variety of different use cases. For example, a practitioner can bundle different combinations analytics together for different story contexts, and the analysis applications can be the component that ties the analytics bundles to different story contexts.

For example, in an example embodiment where a narrative generation system is used to generate narrative stories about structured data from visualizations (e.g., chart data), a practitioner may want different types of narrative stories to be generated for different types of charts. As part of this, a practitioner might decide that, say, Analytics 1, 3, and 5 are useful when generating a narrative story from a line chart, that Analytics 1, 2, and 3 are useful when generating a narrative story from a bar chart, and that Analytics 2, 4, and 5 are useful when generating a narrative story from a histogram. The practitioner can tie different analysis applications to the different chart types (Analysis Application 1 for line charts, Analysis Application 2 for bar charts, and Analysis Application 3 for histograms). When the analysis service is invoked via an analysis request from the authoring service, the analysis service can instantiate and execute a particular analysis application based on the content of the analysis request (e.g., instantiating and executing Analysis Application 1 if the analysis request concerns analysis of line chart data). Analysis Application 1 will then organize and invoke, via the another interface, the analytics that are linked to Analysis Application 1. Parameters and data that are needed by the linked analytics can be passed to the linked analytics via the another interface.

The inventors further note that the lower level analytics can be grouped into different analysis libraries, and these analysis libraries can then be linked to the analysis applications as noted above. These libraries can then further insulate the low level analytics from the higher level applications and thus simplify the design of the analysis applications.

The inventors further disclose that the analysis service can process the structured data to be analyzed to generate new views of that structured data. The analytics within the analysis service can then operate on these new views to improve ability of the system to analyze and call out different perspectives in the resulting narrative while still performing the analysis operations in an efficient manner. For example, aggregation views, filter views, and/or pivot views of the structured data may be helpful to improve the breadth and depth of perspectives revealed in a narrative story as a result of the analysis operations performed by the analytics.

Through these and other features, example embodiments of the invention provide significant technical advances in the NLG arts by separating the logic for narrative story generation from the analysis operations that support such narrative story generation. By structuring coordination between an authoring service and an analysis service via an interface, the modularization of the authoring service and the analysis service allows improvements to be made to one (or both) of these services without adversely affecting the other. Similarly, the use of analysis libraries within the analysis service also allows for specific implementations of individual analytics to be modified and improved without needing to update the interface as a whole.

These and other features and advantages of example embodiments will be discussed in greater detail below.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an example narrative generation computer system in accordance with an example embodiment.

FIG. 2A shows an example narrative generation computer system in accordance with another example embodiment.

FIG. 2B shows an example of how various analytics can be grouped into various analysis libraries.

FIG. 3 shows an example narrative generation computer system in accordance with yet another example embodiment.

FIG. 4 shows an example of how different buckets of analytics can be tied to different types of chart data.

FIG. 5 shows an example process flow for analysis operations within an example embodiment of the analysis service.

FIG. 6 shows an example analytic configuration for an analysis application.

FIG. 7A shows an example process flow for generating an aggregation view of chart data.

FIG. 7B shows example chart data and an example aggregation view produced from such chart data.

FIG. 7C shows an example process flow for generating a filter view of chart data.

FIG. 7D shows example chart data and an example filter view produced from such chart data.

FIG. 7E shows example chart data with example aggregation and filter views produced from such chart data.

FIG. 7F shows an example process flow for generating a pivot view of chart data.

FIG. 7G shows example chart data and an example pivot view produced from such chart data.

FIG. 8A shows an example configuration for a segments analytic.

FIG. 8B shows an example configuration for a peaks analytic.

FIG. 9 shows an example process flow for an example embodiment of an authoring service.

FIG. 10 shows an example process flow for a ranking analytic.

FIG. 11 shows an example process flow for an interactions analytic.

FIG. 12 shows an example process flow for a peaks analytic.

FIG. 13 shows an example process flow for a jumps analytic.

FIG. 14 shows an example process flow for a runs analytic.

FIG. 15 shows an example process flow for a streaks analytic.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

FIG. 1 shows an example narrative generation computer system 100 that employs an authoring service 104 and an analysis service 106 that are separated via an interface 120. The narrative generation computer system 100 can generate a narrative story 144 for a client 140 in response to a story request 142 from the client 140. Client 140 can be a client computer that communicates with the narrative generation computer system 100 via a network such as the Internet, although this need not necessarily be the case. For example, client 140 could also be a client application that is executed by the same computer system that executes the authoring service 104 and analysis service 106

The client 140 can provide a story request 142 to the narrative generation computer system 100 to trigger the generation of a narrative story about a data set such as a set of structured data. The story request 142 can include the structured data. It should also be understood that the structured data need not be included in the story request 142. For example, the story request 142 could alternatively identify a location where the narrative generation computer system 100 can access the structured data. The story request 142 can also include metadata about the structured data that will aid the narrative generation computer system 100 with respect to the type of narrative story that is to be generated. For example, if the structured data is chart data, the story request 142 can include metadata that identifies a chart type for the chart data (e.g., a line chart, bar chart, etc.).

The computer system 100 can execute the authoring service 104 to control the generation of narrative story 144 in response to the story request 142. The authoring service 104 can employ techniques such as those described in the above-referenced and incorporated patents and patent applications to generate narrative stories from data. In these examples, the narrative generation computer system 100 can employ one or more story configurations that specify a narrative structure for desired narrative stories while also specifying parameters that address how the content for such narrative stories is determined.

To support narrative generation in this fashion, the narrative generation computer system 100 will have a need for processing the structured data to generate metadata about the structured data, where such metadata provides the system with further insights about the structured data. As examples, the above-referenced and incorporated patents and patent applications describe various embodiments wherein elements such as derived features, angles, and data characterizations are generated from structured data to support intelligent story generation. For example, if the structured data is a line chart of product sales by month over time, some items of metadata that may be desired to support narrative generation may include (1) the average of product sales per month, (2) the peak value of monthly product sales, (3) an indication as to the direction of product sales over the time period in question (e.g., steadily rising, steadily declining, relatively consistent, highly volatile, etc.) This information serves as metadata about the structured data, and the narrative generation computer system 100 can employ the analysis service 106 to generate such metadata.

Interface 120 serves to modularize the analysis service 106 relative to the authoring service 104, which provides a benefit of shielding the details of the analysis service from the authoring service and vice versa. The authoring service 104 can invoke the analysis service by sending an analysis request 130 to the analysis service 106 via interface 120. This analysis request 130 can be a structured message that includes parameters used to focus and control the analysis operations that are to be performed on the structured data by the analysis service 106. The analysis service 106 then processes the structured data based on parameters in the analysis request 130 to generate desired metadata about the structured data. This metadata can then be returned to the authoring service 104 through interface 120 as analysis results 132.

The authoring service 104 can the use the metadata within the analysis results 132 to support narrative generation in a manner such that the narrative story 144 includes one or more insights about the structured data based on the metadata from the analysis service 106.

The analysis service 106 can also be a multi-layered service where a plurality of analysis applications can selectively invoke any of a plurality of analytics 110 via interface 122. Interface 122 serves to modularize the analytics 110 relative to analysis applications 108, which provides a benefit of shielding the details of the analysis applications from the analytics and vice versa. For example, the analysis applications 108 that are selected and executed with respect to a given analysis request 130 can be context-dependent on the nature of the structured data. By contrast, the analytics 110 can be parameterized so that the logic for the analytics is independent of any specific context with respect to the structured data.

Thus, in an example embodiment, a practitioner may want a first set of analytics 110 to be performed when the structured data is of a first type (e.g., if the structured data corresponds to a line chart) and also want a second set of analytics 110 to be performed when the structured data is of a second type (e.g., if the structured data corresponds to a bar chart). The analysis applications 108 can shield the analytics from such context. With reference to the example of FIG. 1, a first analysis application 108 a can be linked to first analytic 110 a, and another analytic, a second analysis application 108 b can be linked to second analytic 110 b, and so on until an mth analysis application 108 m is linked to the first analytic 110 a, the second analytic 110 b, and an nth analytic 110 n. In this way, the analysis applications selectively invoke and parameterize the desired analytics as a function of the analysis request, and the analytics 110 themselves need not have any conception of the higher level aspects of narrative generation beyond the parameters that are passed to them via interface 122.

Furthermore, if desired by a practitioner, analytics 110 can be linked to analysis applications indirectly via analysis libraries 200 as shown in FIGS. 2A and 2B. An analysis library 200 can be a grouping of one or more analytics 110, and the analysis applications can selectively invoke and parameterize the analysis libraries 200 via interface 122. With reference to the example of FIG. 2A, a first analysis application 108 a can be linked to first analysis library 200 a, and another analysis library, a second analysis application 108 b can be linked to second analysis library 200 b, and so on until an mth analysis application 108 m is linked to the first analysis library 200 a, the second analysis library 200 b, and an zth analysis library 200 z. The various analysis libraries 200 can then group different analytics 110 together in any of a number of combinations. For example, FIG. 2B shows that a first analysis library 200 a can be linked to first analytic 110 a, and another analytic, a second analysis library 200 b can be linked to second analytic 110 b, and so on until a zth analysis library 200 z is linked to the first analytic 110 a, the second analytic 110 b, and an nth analytic 110 n.

FIG. 3 shows an example embodiment of FIG. 2A where the analysis service 106 includes analysis applications 108 that are tailored to different chart types with respect to the structured data. For example, (1) line charts can trigger the analysis service to select a line chart analysis application which is linked to specific analysis libraries such as a time series analysis library and a regression analysis library, (2) bar charts can trigger the analysis service to select a bar chart analysis application which is linked to a specific analysis library such as a cohort analysis library, and (3) histograms can trigger the analysis service to select a histogram analysis application which is linked to specific analysis libraries such as the time series analysis library and the cohort analysis library. As an example, FIG. 4 shows examples of different analytics that a practitioner may want to link to different chart types, together with a description for those analytics. A practitioner can then bundle these different analytics into different analysis libraries as shown by FIG. 2B to define a desired set of analytics to be run when certain chart types are found in the structured data.

FIG. 5 shows an example process flow for an analysis service 106 with respect to the examples of FIGS. 2A and 2B as well as FIG. 3. At step 500, the analysis service 106 processes an analysis request 130 received from the authoring service 104 via interface 120. In an example embodiment, the analysis service 106 can be configured as a web service that responds to analysis requests 130 that, for example, can take the form of HTTP requests from authoring service 104. Such an analysis request 130 can include an unmodified JSON payload that was sent by client 140 to the system 100 as a story request 142. This JSON payload can contain all of the structured data to be considered by system 100. For example, if the system 100 is being used to generate narrative stories about data visualizations, the payload can include all of the data that supports the subject visualization (which may include visualization metadata such as an identification of a visualization type, e.g., line chart, bar chart, etc.). The JSON payload can also include configuration data used for story writing and analytics (e.g., authoring, analytics, drivers, relationships, etc.).

At step 502, the analysis service 106 selects and instantiates an analysis application 108 based on one or more parameters and/or one or more items of structured data in the processed request 130. For example, the analysis service 106 may map a parameter of the request 130 (such as chart type) to a particular analysis application 108. In doing so, the analysis service can build and resolve an analytic configuration based on parameters in the request 130 and any defaults defined by the relevant analysis application 108. This analytic configuration can specify which analytics are to be run and which parameters are to be used in the running of those analytics. In the context of FIGS. 2A and 3, this analytic configuration can specify which analysis libraries 200 are to be invoked, and the analytic configuration may also specify an order of precedence for the analysis libraries that are to be invoked.

FIG. 6 shows an example analytic configuration 600 that can be resolved by the analysis service at step 502 In this example, with reference to FIG. 4, the analysis request 130 will include a parameter that identifies the subject structured data as comprising line chart data. Accordingly, analysis libraries will be invoked that include analytic buckets for segments analysis, trendline analysis, correlation analysis, and volatility analysis. It should be understood that the analytic buckets may include more than one underlying analytic. Accordingly, the analytic configuration 600 will include configurations for specific analyses such as a correlation configuration 602 a, a trendline configuration 602 b, a volatility configuration 602 c, and a segments configuration 602 d. Each specific analysis configuration can include a parameter that identifies the corresponding analytic or analytic bucket as enabled as well as an index parameter 604 that identifies an order of precedence for the corresponding analytic or analytic bucket relative to the other enabled analytics or analytic buckets. In this example, it can be seen that index parameter 604 d identifies the segments analytic bucket as having the highest order of precedence, followed by the trendline analytic bucket (see index parameter 604 b), followed by the volatility analytic bucket (see index parameter 604 c), followed by the correlation analytic bucket (see index parameter 604 a). The order of precedence associated with an analytic can identify an order in which the results of running that analytic are to be expressed in an output narrative. For example, if a streaks configuration has a lower order of precedence than a peaks configuration (and there are valid streaks in the data), then the output narrative would mention streaks-related content before that of peaks (presuming there are peaks in the data).

The analytic configuration 600 can also include specific parameters and/or thresholds to consider for the different specified analytics. For example, to control the trendline analytic bucket, the trendline configuration 604 b can include a parameter 606 that specifies how many prediction periods are to be used in the trendline analysis. The value for this parameter can be passed through via analysis request 130 or it can be defined as a default setting by the analysis service. Thus, it should be understood that user or author preferences for thresholds and the like can be included in the analysis request 130 and applied directly by the analysis service 106 to each of the underlying analytic buckets via a mapping of parameters. This means that when a user or author selects, for example, an inclusion threshold of 0.4 for the segments analysis, any streaks or peaks (which are specific analytics that can be performed as part of segments analytic bucket) that do not exceed a 40% change will be disregarded and not returned in the analysis results 132.

By separating the underlying analytics from the user-driven and/or author-driven configuration in this way, significant flexibility is provided to practitioners for building out new analytics as well as enabling a dynamic and user-defined and/or author-defined content. Engineers can easily prototype as well as selectively enable/disable analytics by updating how analytic buckets are mapped to specific analytics without disrupting user workflows or modifying extensions.

Returning to FIG. 5, at step 504, the selected and instantiated analysis application is executed. The analysis applications 108 can be Python classes which coordinate the ingestion, manipulation and analysis of the structured data. With respect the example of FIG. 4, roughly one analysis application 108 can exist for each chart type supported by system 100, although it should be understood that a practitioner might choose to employ alternate arrangements. For example, a practitioner might choose to have pie charts and bar charts share the same analysis application 108. As another example, a practitioner may want to run different analytics for a single dimensional line chart as compared to a multi-dimensional line chart, in which case the mapping of analysis applications 108 to chart types can take into consideration more than just the high level chart type. The analysis application classes can be configured with knowledge of how to ingest data as well as call out to the generalized analysis libraries 200 that will perform the actual analysis (see steps 510-512). The analysis application 108 will also receive the analysis result(s) 132 from the analysis libraries 200 (step 514) as well as assemble and return the analysis results (step 516) for ultimate delivery to the authoring service 104 (step 506). Steps 516 and/or 506 can include serializing the results and performing transforms on the results to make them understandable to the authoring service 104. As an example, the transforms may convert references in the results from being index-based (e.g., the streak starts at the third dimension value) to being identifier-based (e.g., the third dimension value has an identifier of “d3”). Such a transform can make it easier for the authoring service to find and cache certain values (rather than forcing the authoring service to look through a list of values each time that the value is needed). Such a conversion transformation can be performed by looking through each of the analytic result objects for certain field names (e.g., ‘start_index’ or ‘index’) and replacing the value on that field with the associated dimension value's identifier (e.g., ‘d3’ or “dimension_val_10’).

Each of the analysis application classes can inherit from a base class and thus share a significant amount of logic, particularly with respect to ingestion and high level aspects of the workflow. An area where the analysis application classes may differ is with respect to transform logic as well as in the decisions around which analysis libraries 200 they call out to with which subsets of the structured data.

Which analysis library 200 gets chosen at step 510 can depend on the types of structured data to be analyzed as well as the analytics specified by analytic configuration 600. Some analytics do not lend themselves to analyzing data that does not meet certain criteria. For example, continuity criteria can play a role in deciding whether a peaks analytic should be performed. If the subject data is organized along some form of a continuity basis (e.g., by time), then it may make sense to look for peaks in the data. However, if the data is completely unordered, then the peaks may be deemed arbitrary since the order in the data is arbitrary. Also, some data types and visualizations may have an assumed intent that indicates whether a given analytic would be helpful. An example of this would be where the act of making a line chart implies there is a desire to look at or see trends in the data; hence it makes sense to call out to a time series analysis library if the structured data to be analyzed includes a line chart. Continuing with the examples of FIGS. 3-4, if a line chart story is requested, the time series analysis library 200 can be used to find segments, perform trendline analysis, etc. If drivers are configured for this run, then in addition to the time series analysis library, the regression analysis library 200 can also be called on to run a multivariate regression and assess the model's validity. Similarly, if a histogram story is requested, the cohort analysis library can be called to find outliers/clusters while the time series analysis library will determine the largest jump between histogram bins.

In the case of multi-dimensional structured data, the analysis application 108 can also decide how to split up the multi-dimensional data into new organizations of data which are more amenable to analysis by the specified analytics. These new organizations of the data can help the system find and express more relevant information in a narrative in an efficient manner. By breaking up source multi-dimensional data and analyzing the various pieces independently, the system has a greater ability to efficiently compare and contrast the results to develop a richer and more nuanced story.

For example, the specified analytics may operate to provide more relevant information in a narrative in an efficient manner if they are provided with an aggregated view (or aggregated views) of multi-dimensional chart data. FIG. 7A depicts an example process flow that can be executed to create such an aggregated view of multi-dimensional chart data. Step 700 checks the chart data to see if it is multi-dimensional. If so, step 702 checks to see if a specified analytic would benefit from receiving an aggregated view of the multi-dimensional chart data. If so, step 704 selects the chart dimension(s) to be aggregated. Then, step 706 computes aggregated values with respect to the selected dimension(s). The computed aggregated values are then used to populate a table with an aggregated view of the subject chart data (see step 708). FIG. 7B shows an example of an aggregated view created from a multi-dimensional table with a region dimension, a product dimension, and a monetary sales amount dimension. In this example, the product group dimension is aggregated to produce a regional sales aggregated view where the sales amounts for different product groups in the same regions are aggregated together as shown in FIG. 7B.

As another example, the specified analytics may operate to provide more relevant information in a narrative in an efficient manner if they are provided with a filtered view (or filtered views) of multi-dimensional chart data. This filtered view can also be referred to as a drilldown view. FIG. 7C depicts an example process flow that can be executed to create such a filtered view of multi-dimensional chart data. Step 710 checks the chart data to see if it is multi-dimensional. If so, step 712 checks to see if a specified analytic would benefit from receiving a filtered view of the multi-dimensional chart data. If so, step 704 selects the chart dimension(s) to be filtered, and data is then removed from the chart based on the selected dimension(s) (step 716). Then, step 718 returns a table with the filtered view of the subject chart data. FIG. 7D shows an example of a filtered view created from a multi-dimensional table with a region dimension, a product dimension, and a monetary sales amount dimension. In this example, a filter view of central region sales is desired, which results in the removal of the chart rows corresponding to the western and southern regions as well as removal of the region column given that all of the data in the filtered chart view pertains to the central region.

It should also be understood that the process flows of FIGS. 7A and 7C could be performed in tandem if desired. For example, in a multi-dimensional bar chart run, the analytics application 108 can specify performance of cohort analysis on both a top-level aggregated view of the bar chart data as well as each of a plurality of drilldown views (e.g., sales by region as well as the sales by product in each region). If so, the analysis application can produce both an aggregated view and a filtered view of the chart data for use by the analytics, as shown in FIG. 7E. This would allow analytics to process both the region aggregated view as well as the central region filtered view.

As yet another example, the specified analytics may operate to provide more relevant information in a narrative in an efficient manner if they are provided with a pivoted view (or pivoted views) of multi-dimensional chart data. FIG. 7F depicts an example process flow that can be executed to create such a pivot view of multi-dimensional chart data. Step 720 checks the chart data to see if it is multi-dimensional. If so, step 722 checks to see if a specified analytic would benefit from receiving a pivot view of the multi-dimensional chart data. If so, step 724 selects the measure, primary dimension, and the pivot dimension to be used as part of the pivot operation. Then, step 726 creates a new chart dimension for each unique value in the selected pivot dimension. Next, step 728 populates the values of the selected measure with respect to the selected primary measure into the new chart dimensions. Then, step 730 returns the populated table as the pivot view of the chart data. FIG. 7G shows an example of a pivot view created from a multi-dimensional table with columns for year/month, division, revenue, and sales. In this example, the year month column is used as the primary dimension, the division column is used as the pivot dimension, and the sales column is used as the measure. This results in the pivot view having columns for the two unique values in the pivot dimension (domestic and international) such that the pivot view of sales by division over time appears as shown in FIG. 7G.

Returning to FIG. 5, at step 510, the selected analysis application 108 invokes an analysis library 200 specified by the analytic configuration 600 via interface 122. As previously mentioned, the underlying analytics that power the analysis service 106 can make use of generalized analysis libraries 200 that group together several categories of analytics to achieve a desired purpose. Whereas analysis applications 108 have a notion of chart types and or other higher level aspects relating to the narrative purpose of the narrative generation process, the analysis libraries 200 can be designed to provide a configuration-driven framework for performing computations regardless of a particular context.

At step 520, an invoked analysis library 200 instantiates the one or more analytics within the subject library 200 based on a configuration passed to the library 200 through interface 122. Through the interface 122, the invoked analysis library 200 can receive a data structure (such as a Pandas dataframe) that includes the structured data to be analyzed as well as configuration data for the subject analytics. At step 522, the structured data is processed using the one or more analytics that were instantiated at step 520 to generate analytics-based metadata about the structured data. This metadata is then returned to the analysis application (step 524).

While, for ease of illustration, FIG. 5 shows steps 520-524 being sequentially invoked via a loop between steps 510 and 512, the inventors note that steps 520-524 can be performed in parallel for the different linked analysis libraries if desired by a practitioner. For example, if a processor on which the analysis service runs has multi-processing capabilities, different compute resources can perform steps 520-524 for different linked analysis libraries in parallel with each other (e.g., Compute Resource 1 performs steps 520-524 for linked Analysis Library 1 while Compute Resource 2 performs steps 520-524 for linked Analysis Library 2).

FIG. 8A shows an example of configuration data 800 that can be passed to an analysis library 200 via interface 122. This example configuration 800 is for the segments analysis bucket identified in FIG. 4. The segments analysis specifies three underlying analytics, each with their own configuration 802; namely a configuration 802 a for a Positive Runs analytic, a configuration 802 b for a Peaks analytic, and a configuration 802 c for a Streaks analytic. The configurations 802 specify a parameter mapping for various analytic parameters. The “name” and “calculation type” parameters control where and under what field name on the analysis result model (see 132 in FIG. 1) the calculation results are placed. This can be used by authoring to, for example, discuss all of the “features” in one section, or alternatively by an application developer making use of the analysis service API to have finer-grained control on the output model. The “analytic_name” parameter can be the name of the actual Python class that is to be invoked for the subject analytic (e.g., 110 a in FIG. 1). The configurations 802 can also specify option parameters 804 that influence the results returned by the subject analytic. For example, option parameters 804 a with respect to the Positive Runs analytic specifies a direction to be referenced for measuring runs and also a name for the calculations produced by the positive runs analytic. The direction field can tell the analytic whether to search for always increasing values (positive), always decreasing values (negative), or values that are flat and not change period-over-period. As another example, option parameters 804 b with respect to the Peaks analytic specifies a name for the calculations produced by the peaks analytic. This parameter controls the name of the field to use on the output model for the results of running the “PeaksFeatureFinder” analytic. This could also be used by the authoring service to know where to find that information. As another example, option parameters 804 c with respect to the Streaks analytic specifies a minimum streak length to be used for assessing streaks in the structured data. The minimum streak length parameter can have a value that is expressed as a percentage of the total series length. As mentioned, the specified parameters in configuration 800 can be passed into the analysis service via request 130 or defined as a setting by the analysis service 106 (e.g., analysis application 108 having logic that sets a parameter value as a function of content in the analysis request 130).

With reference to the example of FIG. 3, the time series analysis library 200 can be configured to process structured data that is ordered in some way, and the time series analysis library 200 can bundle analytics that lend themselves to describing the relationship of the values in this structured data with respect to such order. The order can be a time order (such as revenue by month), but the order need not necessarily be a time order. Accordingly, it should be understood that a practitioner might find it useful to apply the time series analysis library 200 to structure that is ordered by some criteria other than time (such as cell phone signal strength by distance from cell tower).

A cohort analysis library 200 can be configured to process unordered data. A practitioner may find it useful to bundle statistical analysis tools in a cohort analysis library (such as analytics that find the skew, mean, etc. with respect to unordered data). Also, analytics that find outliers and clusters of values in a data set may be useful to include in a cohort analysis library.

A regression analysis library 200 enables the performance of regressions on data to create and characterize models. As such, a regression analysis library can unify various stages or steps of regression analysis, including data transformation, model fitting, model evaluation, outlier detection, and prediction. A practitioner might find it useful to permit one or more of these stages to be selectively enabled and disabled via configuration settings passed through interface 122.

Analysis libraries 200 can also specify a workflow of underlying analytics that are to be performed. This allows a number of underlying analytics to be considered as a single atomic unit from a developer's perspective by combining several operations together according to a workflow. Such workflows can take what are typically iterative processes and turns them into a linear operation. For example, the 4 operations outlined below (model fitting/sampling, diagnostic testing, model evaluation, and prediction) are conventionally performed by data scientists until the resulting model (which can take the form of a mathematical expression of relationships associated with certain weights) is sufficient. With an example embodiment, the system can perform this series of steps once in that order, obtaining metadata about how the processed proceeded (e.g., which diagnostic tests were performed, how valid the model is, etc.). The results of these workflows can then expose information about what steps were taken and provide additional information that can contribute to describing the output. For example, the information and the resulting model itself can then be used to report on the results of the process in the narrative (an example of which can be seen in the customer service narrative paragraph below). At each of the 4 operations, the system can accumulate metadata about the process for that operation as well as the results of the operation itself. For diagnostic testing, the system can know which tests were performed for that particular analysis as well as the results of those tests. In such an example, and with reference to the customer service narrative paragraph below, the “there may be other factors contributing the Trip Advisor Score” comment may arise from the fact that one of the diagnostic tests indicated as such, and the statement about “evidence of a very strong relationship” can arise from the model evaluation step. By doing a single pass through the 4 operations described below and reporting out data that indicates how well the models worked out, the system can speed up the analysis processed and lower the bar for performing more advanced analysis without having to understand every underlying detail.

As examples, the times series analysis library and the region analysis library may expose a workflow of underlying analytics to developers as a single atomic unit. For example, a trendline analytic in the time series analysis library and a single/multivariate regression analytic in the regression analysis library can bundle a host of checks and statistics by following a process such as (1) model fitting and sampling, (2) diagnostic testing, (3) model evaluation, and (4) prediction (which may include confidence indicators). Information from each step can be expressed in the analysis results 132, which enables the authoring service 104 to produce a narrative story that expresses insights such as the following:

-   -   “As Customer Service increased, TripAdvisor Score increased         based on the data provided. Specifically, when Customer Service         increased by 10, Trip Advisor Score increased by 3.27. There may         be other factors contributing to Trip Advisor Score, but there         is evidence of a very strong relationship”.

As another example, a periodicity analytic in the time series analysis library, which can be used to find and describe any cyclical behaviors in the structured data, can bundle a series of steps by following a process such as (1) data detrending, (2) periodogram, and (3) white noise bootstrapping (to determine a confidence level). Because the periodicity analytic wants to understand the cyclic nature of values, the bundled steps can help the system understand how often the subject values vary as a function of how often they occur (their frequency). A periodogram, which essentially operates as a histogram here, provides the system with this information by looking at all the values and performing a Fourier Transform on them. The resulting periodogram is then inspected to see at what frequencies the values change the most. As an example, consider a data set that describes ridership of public transportation over time. The frequency information in this would then be to what degree the ridership changes daily, monthly, yearly, etc. The maximum of the transformed data gives the frequency for which the ridership changed the most. The system can then report on those frequencies in the story (saying, for example that the ridership shows cyclicity, adjusting at regular weekly and monthly intervals).

Also, a practitioner may find it useful to include various design patterns and data models within analytics as aids to the story writing process.

For example, rankings are a type of analytic that can be included as part of analysis library, and a ranking analytic can be configured to find the most interesting or important of previously computed analytics. An example process flow for a ranking analytic is shown by FIG. 10. Such ranking calculations can be performed after such other analytics. For example, a rankings analytic could be employed to find a series with the largest positive peak. Similar to the other analytics, a rankings analytic can be configuration-based, where the configuration describes how to find the relevant analytic (e.g., choosing by “compare_calculation_name”) as well as which attribute to look at and compare against (e.g., “compare_attribute” and “compare_strategy”, respectively. An example analytic configuration 802 b for a peaks analytic that includes a ranking analytic configuration 820 is shown by FIG. 8B. The rankings configuration 820 specifies two types of rankings that are to be produced from the results of the peak finding analytic across the various subject series (e.g., measures) in the data. Configuration 822 a specifies how the ranking analytic is to be applied to find the peak within the peak values with the largest positive value. Configuration 822 b specifies how the ranking analytic is to be applied to find the peak within the peak values with the largest negative value. Parameters within these configurations 822 specify control values for the ranking process.

For example, the “as_series” parameter describes how to format that ranking's result. If the “as_series” parameter is set to true, it will link to the entire measure that the peak is associated with (which is what this example wants—the series with the largest positive peak). In other cases, the ranking may want a single value (such as if one wanted to know just the information of the largest positive streak). In that case, the “as_series” parameter would be set to false.

The “filter_attribute” and “filter_value” parameters allow the rankings analytic to have greater control for searching through the various analytic results. The filter attribute and value can restrict the search for all analytic results to those that match the specified criteria. As such, rather than having the ranking analytic look at all the various peaks across all series, it will only rank the ones whose “sign” value is equal to “Positive” as specified by the filter attribute and filter value parameters.

The source data under analysis can be tabular data, where the columns are either dimensions or measures. The series in this data can refer to the various measures in the source tabular data. For example, a source chart may be a line chart that plots sales and revenue over time. The source tabular data in this example includes a time dimension, a sales measure, and a revenue measure. Thus, the sales and revenue values over time can be series data for analysis.

As another example, interactions are another type of analytic that can be included as part of analysis library, and an interactions analytic can be configured to find intersections between data sets. However, it should be understood that the interactions analytic can do more than just find intersections. The interactions analytic can operate on multiple measures, which in practice may include operations such as calculating correlations, finding the intersections between the measure values for continuous data sets, and performing calculations on the series themselves (for example, subtracting one series from another to find the difference). An example process flow for an interactions analytic is shown by FIG. 11. Interactions can be applied to those analytics which use two or more data sets to compute, such as correlation. An interactions analytic can perform steps such as (1) choosing combinations of entities, (2) performing comparisons (e.g., finding intersections, getting correlations, getting differences, etc.), (3) updating compares with reference to analytic results, and (4) trimming/ranking. As an example of an interactions analytic, it may be desirable to find the locations, if any, where three series (A, B, C) converge. The analytic can be configured to by default iterate through pairwise combinations of the series (AB, BC, and AC) and find the intersections within those pairs. If any of these pairs fails to find an intersection (e.g., no intersections are found in the pair AC), then the analytic can stop because the analytic will then know that there are no intersections between all three of the series. This strategy for resolving intersections can greatly reduce computational complexity. Moreover, if desired, such settings could be configurable/over-written.

The inputs for the interactions analytic can be an analysis results container object and a list of groups of measure objects (e.g., pairwise measures A-B, B-C, A-C). As shown by FIG. 11, this process flow creates an interaction result container object which will get populated with results of the interactions analysis. The process flow then loops through the groups, and for each group, it performs comparisons on elements in each group to find intersections, compute correlations, compute differences, etc. and collects results. This operation can have knowledge of the current state of the interactions, and thus has the freedom to abort operations depending on certain conditions (e.g., if no interactions exist for A-C, do not perform the A-B-C intersection comparison operation). Then, the process flow updates the interactions result object with the results of the comparisons.

Some examples of underlying analytics 110 that can be included as part of the analysis service include peaks analytics, jumps analytics, runs analytics, and streaks analytics.

A peaks analytic can be configured to find peaks and troughs within a data set. An example process flow for a peaks analytic is shown by FIG. 12. Peaks and troughs are those features which start at some baseline, move either up or down to some local maxima/minima, then return to that previous baseline. A peaks analytic can identify (1) a baseline value for the data set, (2) absolute and percentage change between the baseline and the peak, (3) locations of the start and end of the peak, (4) the start and end derivatives (which can be the slope of the line made by the values at the first part of the peak and the last part of the peak), and (5) directions of movement between peaks and troughs.

The inputs for the peaks analytic can be the measure values that are to be analyzed to find peaks and the configuration data for the peaks analytic. As shown by FIG. 12, this configuration data can include (1) a min/max width for a peak, (2) a threshold, (3) a percent threshold, (4) a derivative threshold, (5) a sign (or direction, where positive can denote a peak and negative can denote a trough), and (6) a peak report rule (e.g., “nearest real maxima” or “smooth local max value”). As operational steps, the peaks analytic can smooth the series according to the exponentially weighted moving average of the series. Then, the process finds the local maxima/minima of the smoothed data (the points where the derivative is zero). For these local maxima/minima, the analytic gathers information such as their (1) start/end index value, (2) start/end value, (3) width, (4) value at peak (according to configured peak report rule), (5) index value at peak (according to configured peak report rule), (6) start derivative (the slope of the line starting from the start and ending at the center), (7) end derivative (the slope of the line starting from the center and ending at the end), (8) overall derivative (the average of the start derivative and the end derivative), (9) baseline value (the average of the start and end values), (10) change (which can be the height of the peak or the absolute value of the difference between the value at peak and the baseline value), (11) percent change (change divided by baseline value), and (12) score (which can be defined via a function used to give a numeric value to the size of the peak, where the value gets larger for larger changes/percentage changes/derivatives). Next, the analytic can review this information and remove the maxima/minima that do not meet the configuration conditions for the peaks analytic. For example, this step can check that each candidate peak has at least the minimum width, no more than the maximum width/percent change, etc. After this filtering/removal, the remaining peaks and their corresponding data can be returned as information objects.

Jumps are similar to peaks except that instead of returning to the baseline at the start of the peak, the series settles at a new baseline. A jump is a region where the value changes relatively quickly to a new value and then (unlike a peak) stays near the new value for a while. An example process flow for a jumps analytic is shown by FIG. 13. The attributes of a jumps analytic can be similar to those for the peaks analytic except includes the finish baseline value and only the one slope.

The inputs for the jumps analytic can be the measure values that are to be analyzed to find jumps and the configuration data for the jumps analytic. As shown by FIG. 13, this configuration data can include (1) a threshold percent, (2) a minimum series length, (3) window percents (which can be a list of percentages to use for searching for jumps, which corresponds to resolutions of jumps, and which by default can include 50 percentages between 0.2 and 0.75), and (4) retain percents (which specify how long the values must stay relatively similar after the jump and which can be expressed as a percent of the total series length). As operational steps, the jumps analytic can first compare the measure values to the minimum series length configuration. If there are too few values in the data, then the analytic would return no jumps and exit execution. Next, the process creates an absolute threshold based on the threshold percent configuration applied to the difference between the min and max of the data values. Then, the process instantiates an empty list of jumps objects in which the process will accumulate results.

Thereafter, the process attempts to find jumps for each window size. It can identify start/end indices of the center (increasing/decreasing) portion of the candidate jump. This can be done by creating a cuts series by applying a rolling function to the values which (1) splits the values into three portions, (2) compares the average of the first third to the average of the second third, and (3) if the difference between those averages is greater than the threshold percent, mark this region as containing a candidate jump. This step can also find the absolute starts/ends of these regions by noting where the cuts difference between one value and the next is not zero.

The process then adds information to each candidate jump result object. Such information can include (1) a window size, (2) a direction, (3) region information for each of the first/middle/last (i) start/end index, (ii) start/end value, (iii) standard deviation, (iv) mean, and (v) volatility, (4) absolute start/end index (start of first region, end of last region), (5) score (which can be computed via a function used to give a numeric value to the size of the jump, where the value gets larger for larger absolute/percentage changes and jump derivative), and (6) retain length (which can be number of contiguous data points that fall into the retain band, counting from the end of the last region).

Thereafter, the process flow merges jumps across windows. It can look through each jump and build up to larger and larger jumps by combining the jump information if the locations of the starts and ends overlap. Next, the analytic can filter out jumps according to the configured stay time (retain percent). From there, the remaining jumps can be returned as jump objects according to scores.

A runs analytic can be configured to find a sub-array within a series (single region) whose summed values gives the largest amount. A positive/negative run can be defined as a contiguous subarray of numbers whose forward differences sum to a global positive/negative maximum. Such a sub-array can be referred to as the maximum value sub-array, and this type of analysis can be useful for describing regions which impacted net growth/decline. For example, for the array [2, 1, 2, 4, 3, 5, 4, 3, 4], the maximum net positive run is [1, 2, 4, 3, 5], and the maximum net negative run is [5, 4, 3] (where the run length is greater than or equal to 2). An example of a narrative story that can express an insight derived from a runs analytic can be:

-   -   “Contrasting with the overall decrease, the largest net growth         was from March 2007 to October 2007, when Central Revenue rose         by 1.6 million (135%).”

FIG. 14 shows an example process flow for a runs analytic. The inputs for the runs analytic can be the measure values that are to be analyzed to find runs and a configured run direction. If the run direction is negative, the analytic multiplies all values by −1. Next, the analytic finds the maximum value subarray. To do so, it can (1) instantiate current sum, start index/end index for subarray to 0, (2) instantiate final max sum, start/end index for the best subarray to 0, (3) and iterate through the measure values. As part of these iterations, the analytic can (1) if the current value plus the current sum is greater than 0, add the current value to the current sum, (2) otherwise, reset the current sum start location to the current index, and (3) if the current sum is greater than the final sum, overwrite the final sum with the current sum and the current start/end index. After completing the iterations, the analytic returns the final maximum subarray. It then collects additional information about this subarray, such as percent and absolute difference between the start and end of the run, the run length, etc.

A streaks analytic can be configured to find streaks within a data set, where streaks can be defined as consecutively increasing/decreasing/unchanging regions of the data set. For example, given the series [3, 3, 3, 4, 5, 2, −1], there are three streaks present—[3, 3, 3] which is a flat streak, [3, 4, 5] which is a positive streak, and [5, 2, −1] which is a negative streak (where the streak length is greater than or equal to 2). Similar to peaks, a streaks analytic can identify (1) the start/end locations for streaks, (2) absolute and percentage change for start to finish for each streak, (3) the direction of movement for each streak, and (4) the length for each streak. Unlike runs, streaks are consistently increasing/decreasing/unchanging with respect to defined thresholds. Streaks can be thought of in a sports context as being, for example, when a basketball player has made all of his shots taken in a quarter. Runs, on the other hand, would be used to describe the period where the winning team pulled ahead the most.

FIG. 15 shows an example process flow for a streaks analytic. The inputs for the streaks analytic can be the measure values that are to be analyzed to find streaks and configuration data for the streaks analytic. The configuration data can be used to control the streaks analytic to only expose streaks of certain types or longer than a certain length. The streaks configuration data can include (1) a streak type (positive, negative, and/or flat), (2) a minimum streak length, and (3) a sort configuration (e.g., sort on streak length then on streak type).

As an operational step, the analytic finds the streak ends/starts using the measure values. This can include (1) creating an array of values corresponding to the difference between consecutive measure values (deriv), (2) finding the regions where the difference is positive (pos_deriv), (3) finding the regions where the difference is zero (flat_deriv), and (4) identifying the starts of the regions by comparing the positive/flat derivative to shifted values (so 1, 1, 1, 2, 2, =>True, False, False, True, False).

As a next operational step, the analytic determines streak direction for each streak by taking the difference of the start and end value for each of the streaks (diff>0=>positive, etc.).

As another operational step, the analytic creates streak result objects. These objects can get populated with information such as start/end index, start/end value, direction, and length. Thereafter, the analytic can filter out invalid streaks based on the streak configuration data. For remaining streaks, the analytic can add additional information to the streak objects such as absolute/percent difference information, and then return all streak objects, as sorted according to the sort configuration.

FIG. 9 depicts an example process flow for the authoring service 104. At step 900, the authoring service receives structured data with respect to a story request 142. This structured data is the data to be described by the narrative story. Optionally, this structured data may be included as part of the story request 142. At step 902, the authoring service parameterizes a story configuration based on the structured data and the story request 142. Examples of such configurations are described in the above-referenced and incorporated patents and patent applications. For example, the '844 and '178 patents describe a configuration-based approach for narrative generation that employs story specifications and content blocks. As another example, patent application Ser. Nos. 15/253,385, 15/666,151, 15/666,168 and 15/666,192 describe a configuration-based narrative generation technique in connection with generating narratives from visualization data. As yet another example, the '899, '492, '197, and '009 patents and patent applications 62/460,349, 62/539,832, and 62/585,809 describe a configuration-based approach for narrative generation that employs explicit representations of communication goals to help drive narrative generation.

The authoring service can then process the story configuration to determine that analytics are needed to compute additional data needed for the story generation process, and a call can be made to analysis service 106 via interface 120 for this purpose (step 904). As discussed above, the authoring service can communicate, via interface 120, an analysis request 130 to the analysis service 106, where such an analysis request 130 can includes configuration information for the analysis operations. At step 906, the authoring service receives the analysis results 132 from the analysis service 106 via interface 120. These analysis results are ingested into the story configuration at step 908, and a determination is made as to whether more analysis is needed (step 910). If more analysis is needed, the process flow returns to step 904. Otherwise, the process flow proceeds to step 912. At step 912, a narrative story 144 about the structured data is generated based on the story configuration, and this narrative story 144 can express insights about the structured data that results from the analysis results returned by the analysis service 106. For example, the narrative story might identify the values of the largest peaks in a data set. The above-referenced patents and patent applications describe how narrative stories can be generated from story configurations in this fashion. Lastly, at step 914, the authoring service returns the narrative story 144 to the client 140 in response to the request. This step may involve encoding the narrative story as an HTML document or the like to facilitate presentation via a web page.

Returning to FIGS. 1-3, the computer system 100 may comprise a processor and a memory that are operatively coupled with each other. The computer system may also include additional components such as a network interface. The computer system components can be interconnected with each other in any of a variety of manners (e.g., via a bus, via a network, etc.). The processor may comprise one or more processors such as general-purpose processors (e.g., a single-core or multi-core microprocessor) etc. that are suitable for carrying out the operations described herein. The memory may comprise one or more non-transitory computer-readable storage mediums, such as volatile storage mediums (e.g., random access memory, registers, and/or cache) and/or non-volatile storage mediums (e.g., read-only memory, a hard-disk drive, a solid-state drive, flash memory, and/or an optical-storage device). The memory may also be integrated in whole or in part with other components of the system 100. Further, the memory may be local to the processor, but it should be understood that the memory (or portions of the memory) could be remote from the processor (in which case the processor may access such remote memory through a component such as a network interface). The memory may store software programs or instructions that are executed by the processor during operation of the system 100. For example, the memory may store the authoring service 104 and the analysis service 106. Furthermore, it should be understood that the computer system 100 could include multiple processors and memories arranged as a distributed computing architecture. With such an arrangement, analytics that are amenable to parallel execution can be executed in parallel by different compute resources within the distributed computing architecture. Furthermore, if the system 100 is handling a large load of story requests 142, the narrative generation tasks performed by the authoring service and analysis service with respect to the various story requests 142 can be distributed across different processors within the distributed computing architecture. Such an approach can yield lower latency with respect to story production.

While the invention has been described above in relation to its example embodiments, various modifications may be made thereto that still fall within the invention's scope. Such modifications to the invention will be recognizable upon review of the teachings herein. 

What is claimed is:
 1. An apparatus for applying artificial intelligence to generate a narrative story from structured data, the apparatus comprising: a processor and a memory that are operatively coupled with each other and comprise (1) an authoring service and (2) an analysis service; wherein the authoring service is segregated from the analysis service through an interface; wherein the analysis service is (1) invocable by the authoring service through the interface and (2) configured, in response to invocation by the authoring service through the interface, to (i) generate metadata about the structured data and (ii) communicate the metadata to the authoring service; wherein the authoring service is configured to (1) receive the structured data, (2) invoke the analysis service through the interface at runtime based on the structured data, and (3) process the structured data and the communicated metadata in accordance with a story configuration to generate a narrative story that expresses an insight about the structured data based on the communicated metadata; and wherein the analysis service is further configured to (1) generate a new organization of the structured data and (2) process the new organization of structured data to generate the metadata.
 2. The apparatus of claim 1 wherein the analysis service is further configured to generate a new organization of the structured data by performing a pivot operation on the structured data that is arranged in a plurality of rows and columns.
 3. The apparatus of claim 2 wherein the structured data comprises multi-dimensional line chart data.
 4. The apparatus of claim 1 wherein the analysis service is further configured to generate a new organization of the structured data by performing an aggregation operation on the structured data that is arranged in a plurality of rows and columns.
 5. The apparatus of claim 4 wherein the structured data comprises multi-dimensional bar chart data.
 6. The apparatus of claim 1 wherein the analysis service is further configured to generate a new organization of the structured data by performing a filter operation on the structured data that is arranged in a plurality of rows and columns.
 7. The apparatus of claim 6 wherein the structured data comprises multi-dimensional bar chart data.
 8. The apparatus of claim 1 wherein the authoring service is further configured to communicate a structured message to the analysis service through the interface to invoke the analysis service.
 9. The apparatus of claim 8 wherein the analysis service is further configured to selectively perform a plurality of different analysis operations, and wherein the authoring service is further configured to selectively invoke a subset of the analysis operations based on a parameter in the structured message.
 10. The apparatus of claim 9 wherein the structured message parameter comprises a plurality of parameters in the structured message.
 11. The apparatus of claim 9 wherein the structured message further comprises at least a portion of the structured data from which the narrative story is generated; and wherein the authoring service is further configured to selectively invoke a subset of the analysis operations based on (1) the structured message parameter and (2) structured data within the structured message.
 12. The apparatus of claim 9 wherein the analysis service is further configured to (1) resolve an analytics configuration based on the structured message, (2) instantiate an analytics application based on the analytics configuration, (3) execute the instantiated analytics application to selectively invoke a subset of the analysis operations, and (4) receive and serialize a plurality of results from the selectively invoked subset of analysis operations.
 13. The apparatus of claim 12 wherein the analytics configuration specifies an order of precedence for the subset of analysis operations.
 14. The apparatus of claim 12 wherein the analytics configuration specifies a parameter value for use in controlling at least one of the subset of analysis operations.
 15. The apparatus of claim 14 wherein the parameter value comprises a threshold value.
 16. The apparatus of claim 14 wherein the structured message includes the parameter value.
 17. The apparatus of claim 1 wherein the structured data comprises visualization data.
 18. The apparatus of claim 17 wherein the visualization data comprises at least one of line chart data, bar chart data, histogram data, pie chart data, and/or scatterplot data.
 19. The apparatus of claim 1 wherein the analysis service is configured as a web service.
 20. The apparatus of claim 1 wherein the processor and memory comprise a plurality of processors and memories.
 21. The apparatus of claim 20 wherein the processors and memories are arranged as a distributed computing architecture.
 22. A computer program product for applying artificial intelligence to generate a narrative story from structured data, the computer program product comprising: a plurality of processor-executable instructions that are resident on a non-transitory computer-readable storage medium, the instructions comprising (1) a first plurality of the instructions arranged as an analysis service and (2) a second plurality of the instructions arranged as an authoring service; wherein the analysis service is segregated from the authoring through an interface; wherein the analysis service is (1) invocable by the authoring service through the interface and (2) configured, in response to invocation by the authoring service through the interface, to (i) generate metadata about the structured data and (ii) communicate the metadata to the authoring service; wherein the authoring service is configured to (1) receive the structured data, (2) invoke the analysis service through the interface at runtime based on the structured data, and (3) process the structured data and the communicated metadata in accordance with a story configuration to generate a narrative story that expresses an insight about the structured data based on the generated communicated metadata; and wherein the analysis service is further configured to (1) generate a new organization of the structured data and (2) process the new organization of structured data to generate the metadata.
 23. The computer program product of claim 22 wherein the analysis service is further configured to generate a new organization of the structured data by performing a pivot operation on the structured data that is arranged in a plurality of rows and columns.
 24. The computer program product of claim 23 wherein the structured data comprises multi-dimensional line chart data.
 25. The computer program product of claim 22 wherein the analysis service is further configured to generate a new organization of the structured data by performing an aggregation operation on the structured data that is arranged in a plurality of rows and columns.
 26. The computer program product of claim 25 wherein the structured data comprises multi-dimensional bar chart data.
 27. The computer program product of claim 22 wherein the analysis service is further configured to generate a new organization of the structured data by performing a filter operation on the structured data that is arranged in a plurality of rows and columns.
 28. The computer program product of claim 27 wherein the structured data comprises multi-dimensional bar chart data.
 29. The computer program product of claim 22 wherein the authoring service is further configured to communicate a structured message to the analysis service through the interface to invoke the analysis service.
 30. The computer program product of claim 29 wherein the analysis service is further configured to selectively perform a plurality of different analysis operations, and wherein the authoring service is further configured to selectively invoke a subset of the analysis operations based on a parameter in the structured message.
 31. The computer program product of claim 30 wherein the structured message parameter comprises a plurality of parameters in the structured message.
 32. The computer program product of claim 30 wherein the structured message further comprises at least a portion of the structured data from which the narrative story is generated; and wherein the authoring service is further configured to selectively invoke a subset of the analysis operations based on (1) the structured message parameter and (2) structured data within the structured message.
 33. The computer program product of claim 30 wherein the analysis service is further configured to (1) resolve an analytics configuration based on the structured message, (2) instantiate an analytics application based on the analytics configuration, (3) execute the instantiated analytics application to selectively invoke a subset of the analysis operations, and (4) receive and serialize a plurality of results from the selectively invoked subset of analysis operations.
 34. The computer program product of claim 33 wherein the analytics configuration specifies an order of precedence for the subset of analysis operations.
 35. The computer program product of claim 33 wherein the analytics configuration specifies a parameter value for use in controlling at least one of the subset of analysis operations.
 36. The computer program product of claim 35 wherein the parameter value comprises a threshold value.
 37. The computer program product of claim 35 wherein the structured message includes the parameter value.
 38. The computer program product of claim 22 wherein the structured data comprises visualization data.
 39. The computer program product of claim 38 wherein the visualization data comprises line chart data.
 40. The computer program product of claim 38 wherein the visualization data comprises bar chart data.
 41. The computer program product of claim 38 wherein the visualization data comprises histogram data.
 42. The computer program product of claim 38 wherein the visualization data comprises pie chart data.
 43. The computer program product of claim 38 wherein the visualization data comprises scatterplot data.
 44. The computer program product of claim 22 wherein the analysis service is configured as a web service.
 45. The computer program product of claim 22 wherein the non-transitory computer-readable storage medium comprises a plurality of non-transitory computer-readable storage mediums. 